Additional Implementation Activities for All Finance Apps
Note
If you use “SAP Fiori Cloud for SAP S/4HANA”, this information is not relevant for you. You don’t need to install individual apps. Instead, you connect your back-end system to the SAP Cloud Platform.
For more information, see the product documentation for “SAP Fiori Cloud for SAP S/4HANA” on the SAP Help Portal at http://help.sap.com/fioricloud_s4hana
.
Start your app implementation by following the tasks described in the “UI Technology Guide for SAP S/4HANA” for this release, which is available at http://help.sap.com/s4hana
. .
For the technical information, such as OData services and catalogs, that you need to implement an individual app, go to the “SAP Fiori apps reference library” at https://boma0d717969.hana.ondemand.com/sap/fix/externalViewer/![]()
Complete the implementation activities specific to Finance apps, which are described in the following sections.
If you need more help, try the “SAP Fiori - Troubleshooting Guide for Financial Apps”, which is available on the SAP Community Network at http://scn.sap.com/docs/DOC-70278![]()
The SAP Fiori Launchpad (FLP) contains a user default parameter service that calls application plug-ins for the FLP. For the display and use of the finance apps delivered with SAP S/4HANA , on-premise, the fin.central.user.defaultparameter
application plug-in is needed.
Register the fin.central.user.defaultparameter
application plug-in for use by following these steps:
Activate the FIN_USER_DEFAULTPARAMETER
OData service on your ABAP front-end server.
To do this, use the /IWFND/MAINT_SERVICE transaction and add this service. Alternatively, you can activate the services in the SAP Customizing Implementation Guide (SPRO transaction) under .
Note
If you have multiple ABAP back-end servers, you must activate the FIN_USER_DEFAULTPARAMETER_SRV
technical services on each ABAP back-end server by listing each system alias.
The activation on the ABAP front-end server triggers automatically the activation of the FIN_USER_DEFAULTPARAMETER_SRV
technical service on your ABAP front-end server. You can check this using the SICF transaction. Check under .
Activate the FIN_ACC_USERPAR ICF
service on your ABAP front-end server. Use the SICF transaction and check under .
The fin.central.user.defaultparameter
application plug-in is called for determining the value for certain user default parameters (for example, company code) from the ABAP back end. The plug-in is called in two situations:
A Fiori app is started that requires a certain user default parameter.
The FLP maintenance UI for the user default parameter is opened.
The FLP has its own persistency on the ABAP front-end server for storing the user default parameters. By default, all parameters are read from this persistency. If a parameter is not yet stored in the FLP persistency, then the application plug-in calls the back end for determining the parameter value.
Activate the following ICF service on your ABAP front-end server by using the SICF transaction:
Component | Technical Name | SAP Note |
|---|---|---|
|
|
For apps that have Transactional (Generic UI5 Job Scheduling Framework)
as their application type in the “SAP Fiori apps reference library” , ensure that the UIBAS001
software component is also installed on your front-end server. These apps need generic services and UIs in this software component to run properly.
The “SAP Fiori apps reference library” is available at https://boma0d717969.hana.ondemand.com/sap/fix/externalViewer/
.
For apps that have Analytical (Smart Business generic Drill Down App)
as their application type in the “SAP Fiori apps reference library”, ensure that the /SSB/SMART_BUSINESS_RUNTIME_SRV (1)
OData service is activated. These apps need this OData service to run properly.
For more information about activating OData services, see section Front-End Server: Activate OData Services
in the SAP S/4HANA “UI Technology Guide” available at http://help.sap.com/s4hana
.